Cellular IoT network architecture

ABSTRACT

This document discusses, among other things, a Cellular Internet-of-Things (CIoT) network architecture to enable communication between an apparatus of a CIoT User Equipment (UE) and a network through a CIoT enhanced Node B (eNB) according to a lightweight Non-Access Stratum (NAS) protocol. An apparatus of a CIoT eNB can process data for communication between the CIoT UE and the network. The lightweight NAS protocol supports a reduced set of NAS messages for communication between, for example, the CIoT UE and the CIoT eNB, such as using a modified NAS message, or one or more new messages.

CLAIM OF PRIORITY

This application is a continuation of U.S. patent application Ser. No.15/573,153, filed Nov. 10, 2017, which is a U.S. National Stage Filingunder 35 U.S.C. 371 from International Application No.PCT/US2015/000298, filed on Dec. 23, 2015, and published as WO2016/200357 on Dec. 15, 2016, which claims the benefit of priority ofJain et al., U.S. Provisional Patent Application Ser. No. 62/174,110,entitled “NETWORK AND SECURITY ARCHITECTURE FOR CELLULAR IOT,” filed onJun. 11, 2015, each of which are hereby incorporated by reference hereinin their entirety.

TECHNICAL FIELD

This document relates generally to cellular communication and moreparticularly to network and security architecture for CellularInternet-of-Things (CIoT) communication.

BACKGROUND

Machine-to-Machine (M2M) communication represents a significant growthopportunity for the 3rd Generation Partnership Project (3GPP) ecosystem.With proliferation of the wireless networks, there is an acceleratedpush towards connected, smart physical objects, such as wirelesssensors, smart meters, dedicated microprocessors, etc., that spandifferent ecosystems with diverse business models.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. Like numerals havingdifferent letter suffixes may represent different instances of similarcomponents. The drawings illustrate generally, by way of example, butnot by way of limitation, various embodiments discussed in the presentdocument.

FIG. 1 illustrates generally an example Cellular Internet-of-Things(CIoT) network architecture including a CIoT User Equipment (UE), a CIoTAccess Network (CAN), and a network.

FIG. 2 illustrates generally an example CIoT Access Network (CAN)including a CIoT enhanced Node B (CIoT eNB) and a CIoT Access NetworkGateway (GW).

FIG. 3 illustrates generally an example CIoT network securityarchitecture.

FIG. 4 illustrates generally an example CIoT attach procedure.

FIG. 5 illustrates generally an example CIoT mobile originated (MO)small data transfer.

FIG. 6 illustrates generally an example CIoT mobile terminated (MT)small data transfer.

FIG. 7 illustrates generally a block diagram of an example UE upon whichone or more embodiments may be implemented.

FIG. 8 illustrates generally a block diagram of an example machine uponwhich any one or more of the techniques discussed herein may perform.

DETAILED DESCRIPTION

Next generation mobile networks (NGMN), 5G and beyond, will becharacterized by the existence of multiple types of access technologies,multi-layer networks, multiple types of devices, etc. In such anenvironment, there is a fundamental need for enablers to achieveseamless and consistent user experience across time and space.

The present inventors have recognized, among other things, network andsecurity architecture for communication between CellularInternet-of-Things (CIoT) devices (e.g., User Equipment (UE)) and anetwork (e.g., according to 3GPP standards) that address one or more ofthe following usage scenarios: low throughput; delay tolerant; powerefficient (e.g., having battery life of years or greater); coverage inchallenging conditions (e.g., indoor and underground); and ultra-lowcost, to be disposable or deployable on a mass scale.

FIG. 1 illustrates generally an example CIoT network architecture 100(e.g., clean slate architecture) including a Cellular Internet-of-Things(CIoT) User Equipment (UE) 102 configured to communicate with a network108 through a CIoT Access Network (CAN) 104. The CAN 104 can include aCIoT Base Station, such as an CIoT enhanced Node B (eNB), and a CIoTGateway (GW), such as illustrated in FIG. 3, below.

In an example, the CIoT UE 102 can include, among other things,processing circuitry and a radio interface, such as illustrated in FIG.7, below. The processing circuitry can process data for communicationwith the network 108 through the CAN 104 according to a lightweightNon-Access Stratum (NAS) protocol, and the radio interface cancommunicate with the CAN 104 using a first reference point (C1) 112,such as a narrowband air interface, for example, based on one or moreclean slate, low-power, wide area technology, such as narrowbandOrthogonal Frequency-Division Multiplexing (OFDM), SIGFOX, Neul, etc.).

In an example, the lightweight NAS protocol can support a reduced set ofNAS messages for communication between the CIoT UE 102, or one or moreother CIoT devices, and the CAN 104. The lightweight NAS protocol canterminate on the network 108 side of the CAN 104, such as in a CIoT GW,etc. In an example, the reduced set of NAS messages is exclusive ofmobile NAS messages (e.g., messages required to support mobility), suchas, in certain examples, at least one of handover (HO) or tracking areaupdate (TAU). In certain examples, the processing circuitry of the CIoTUE 102 can be configured to receive a modified NAS message that includescommunication data from the network 108, or to modify an existing NASmessage to include data for communication to the network 108. In certainexamples, the lightweight NAS protocol can support simple uplink anddownlink data transport between the CIoT UE 102 and the network 108,such as through the CAN 104 or one or more other network component, thatcan piggy back on an existing initial entry message, such as one or moreof an attach message, a service request message, or one or more otherperiodic messages (e.g., periodic TAU, etc.). In other examples, one ormore other new lightweight transport messages can be defined.

In this example, the CIoT network architecture 100 includes a ServiceCapability Exposure Function (SCEF) module 106, and a Home SubscriberServer (HSS) or an Authentication, Authorization, and Accounting (AAA)server 110, or a server having one or more HSS/AAA functions. Thenetwork 108 can include a packet data network, an operator network, or acloud service network, having, for example, among other things, aService Capability Server (SCS), an Application Server (AS), or one ormore other external servers or network components.

The CAN 104 can be coupled to the HSS/AAA server 110 using a secondreference point (C2) 118, including, for example, an air interface basedon an S6a reference point, and configured to authenticate/authorize CIoTUE 102 access to the CAN 104. The CAN 104 can be coupled to the network108 using a third reference point (C3) 122, including, for example, anair interface corresponding to an SGi/Gi interface for 3GPP accesses.The CAN 104 can be coupled to the SCEF module 106 using a fourthreference point (C4) 114, including, for example, an air interface basedon a T6a/T6b reference point, for service capability exposure. The SCEFmodule 106 may act as an API GW towards a 3rd party application server.The SCEF 106 can be coupled to the HSS/AAA server 110 using an S6treference point, and to the network 108 using an Application ProgrammingInterface (API) 116.

In certain examples, one or more of the CIoT devices disclosed herein,such as the CIoT UE 102, the CIoT AN 104, etc., can include one or moreother non-CIoT devices, or non-CIoT devices acting as CIoT devices, orhaving functions of a CIoT device. For example, the CIoT UE 102 caninclude a smart phone, a tablet computer, or one or more otherelectronic device acting as a CIoT device for a specific function, whilehaving other additional functionality.

FIG. 2 illustrates generally an example CIoT Access Network (CAN) 104including a CIoT enhanced Node B (CIoT eNB) 202 and a CIoT AccessNetwork Gateway (GW) 204. In certain examples, the CAN 104 can includemultiple base stations (e.g., CIoT eNBs) connected to the CIoT GW 204.In certain examples, internal architecture of CAN 104 may be left to theimplementation and need not be standardized.

In an example, the CIoT GW 204 can include functionality of one or moreof an Evolved Packet System (EPS) Mobile Management Entity (MME),Serving Gateway (S-GW), and Packet Gateway (P-GW). The CIoT eNB 202 canbe coupled to the CIoT GW 204 using a connectionless S1-lite interface,such as disclosed in the commonly assigned Jain et al., U.S. applicationSer. No. 14/126,252, titled “Always-On Bearer for Small Data Transfersin LTE Systems,” included by reference herein in its entirety, includingits disclosure of an S1-U interface between the eNB and the S-GW.

An apparatus of the CAN 104 may perform, among other things, one or moreof: authentication; authorization; UE reachability procedures; packetrouting and forwarding; mobility anchor; L2 data tunneling with CIoT UE;or DHCP client, such as a destination IP for an application server.

In an example, one or more of the CIoT eNB 202 or the CIoT GW 204 caninclude processing circuitry and a radio interface, similar to that inthe CIoT UE described in FIGS. 1 and 7. In an example, the processingcircuitry can process data for communication between CIoT UE and anetwork according to the lightweight NAS protocol, such as describedherein, and the radio interface can communicate with the CIoT UE using afirst reference point, such as the first reference point (C1) 112described above. In an example, the processing circuitry can modify anexisting NAS message, or create a new message, to include data forcommunication to the CIoT UE, or receive data in a modified NAS message,or a new message, from the CIoT UE for communication to the network. Inan example, the existing NAS message includes an attach message or aservice request message, or, in certain examples, one or more periodicmessages, such as a periodic tracking area update (TAU) message.

FIG. 3 illustrates generally an example CIoT network securityarchitecture 300 having two deployment options: within an operatornetwork 318; and within a service provider network 328 (e.g., Google,Google cloud, etc.).

The operator network 318 can include, for example, a CIoT eNB 304, aCIoT GW 305, an Application Server (AS) 308, a Home Subscriber Server(HSS) 312, an Authentication Center (AUC) 314, and a Service CapabilityExposure Function (SCEF) module 316. The CIoT GW 305 can include one ormore functions of an MME, an S-GW, or a P-GW. Accordingly, the CIoT GW305 of FIG. 3 includes a CIoT S-GW 306, a CIoT P-GW 307, and a CIoT MME310.

The CIoT eNB 304 can be coupled to the CIoT GW 305, for example, to theCIoT S-GW 306, using an S1-lite interface, such as described above. TheCIoT GW 305 can be coupled to the AS 308, such as through the CIoT P-GW307, using an SGi interface. The CIoT S-GW 306 can be coupled to theCIoT MME 310 using a C2 interface, and the CIoT MME 310 to the HSS 312.The CIoT GW 305 can be coupled to the SCEF 316 using a C4 interface,such as between the CIoT MME 310 and the SCEF 316. In other examples,one or more of these components can be omitted, or other interfaces canbe used.

The service provider network 328 can be coupled to the operator network318 using, for example, a network 320 (e.g., using the internet) or adata center 322, and can include, among other things, a Gateway (GW) 324and a network 326.

When service application is outside the operator network 318, and withinthe service provider network 328, the CIoT GW 305 can be placed directlyafter the CIoT eNB 304. The CIoT GW 305 can be the bridge (for the dataplane) between the operator network 318 and the service provider network328. Encrypted Layer 2 packets from the CIoT UE 302 can be tunneled fromthe CIoT eNB 304 to the CIoT GW 305. In this example, the CIoT networksecurity architecture 300 can deploy one or more security solutions,such as Hop-by-hop security, Application security, etc. Hop-by-hopsecurity can provide security between the CIoT UE 302 and the CIoT GW305, or between the CIoT GW 305 and the service provider network GW 324.Application security can provide end-to-end security between the CIoT UE302 and an application server inside the operator network 318 (e.g., acloud service network).

When service application is inside the operator network 318, anapplication server (AS) 308 can be placed inside the home network, andencrypted Layer 2 packets from the CIoT UE 302 can be tunneled from theCIoT eNB 304 to the AS 308. In this example, the CIoT network securityarchitecture 300 can deploy one or more security solutions, such asHop-by-hop security, Application security, etc. Application security canbe used between the CIoT UE 302 and the AS 308. Hop-by-hop security canbe used between the CIoT UE 302 and the CIoT eNB 304, or between theCIoT eNB 304 and the AS 308.

In an example, when an application server (AS) resides in a remote cloudservice network, the CIoT UE 302 can authenticate to a network (e.g., anetwork 326 of service provider network) using UMTS-AKA with a specificAPN that indicates the CIoT UE 302 is layer-2 COIT. Upon successfulauthentication, security end-points can be established between the CIoTUE 302 and the Security GW, and the CIoT MME 310 can send KASME, theCIoT UE 302 layer-2 address, and APN address (e.g., can map to cloudapplication server IP address) to the Security GW over I2. The CIoT MME310 can set a state in the CIoT eNB 304 indicating layer-2 forwardingfor this CIoT UE 302 over I2. The Security GW can create a routing tablebased on the information received over I2 for this CIoT UE 302.

Further, when the AS resides in a remote cloud service network, packetflow from the CIoT UE 302 to the cloud application server can includeencrypted layer-2 payload to the CIoT eNB 304 from the CIoT UE 302. TheCIoT eNB 304 can forward the encrypted layer-2 payload to the CIoT GW305 over I1. The Security GW can decrypt the layer-2 payload, and tunnelthe payload to the cloud security gateway over an encrypted pipe. Packetflow from the cloud application server to the CIoT UE 302 can be thereverse of above.

FIG. 4 illustrates generally an example CIoT attach procedure 400including a CIoT UE 402, a CIoT eNB 404, a CIoT GW 406, an HSS 408, and,in roaming scenarios, a Packet Data Network Gateway (P-GW) 410. Incertain examples, as used herein, the CIoT GW 406, or one or more otherCIoT GW referenced herein, can be referred to as a CIoT Serving GatewayNode (C-SGN).

At 4.0, an RCC connection can be established. At 4.1, the CIoT UE 402performs an Attach Procedure, for example, sending an Attach Request(e.g., CIoT Attach, Data Type) to the CIoT GW 406, such as through theCIoT eNB 404. During the Attach Procedure, the CIoT UE 402 can indicatethat this attach is for CIoT communication. The CIoT eNB 404 can selecta CIoT GW 406 optimized for CIoT based on the UE indication or based onone or more pre-configurations. The CIoT UE can also indicate a specificData Type (e.g. IP, non-IP, SMS, or a combination of one or more ofthese or others). Further, an APN may be indicated.

At 4.2, the CIoT GW 406 can perform any necessary authentication orsecurity procedures. At 4.3, a location update and retrieval ofsubscription information can optionally occur. In certain examples, thisand other functions noted with a dotted line can be omitted, dependingon the requirements of communication between the CIoT UE and CIoT eNB404, or the type of CIoT UE 402.

At 4.4, the CIoT GW 406 can processes the Attach Request message and, inthe roaming scenario, send a Create Session Request (e.g., a CIoTAttach, Data Type, etc.) to the P-GW 410. In certain examples, based onparameters provided, an IP Bearer service can be established.

For example, for a Data Type of IP, the PDN type can indicate a type ofIP address (e.g., IPv4, IPv6) to be allocated. the CIoT GW 406 canallocate an IP address based on the PDN type in the attach request. Incertain examples, NAS Session Management Signaling is not required. Inthe roaming case, the CIoT GW 406 can send a Create Session Request tothe P-GW 410 to indicate that this is an Attach for a CIoT UE and DataType. The P-GW 410 can allocate an IP address based on the PDN type inthe Attach Request.

For a Data Type of non-IP, the CIoT GW 406 does not run any IP-relatedoperation (e.g., IP address allocation, etc.). Based on theconfiguration, the CIoT GW 406 may establish a direct forwarding path(e.g., a point-to-point tunnel on per UE, per PDN basis, towards AS,etc.). Alternatively, based on the configuration and if an SCEF isdeployed, the CIoT GW 406 may decide to route small data via the SCEF.In this case, no Create Session Request is required to be sent to theP-GW 410. In certain examples, the configuration can be based oncriterion such as an SLA between an operator and a third partyapplication service provider, or one or more other criterion.

For a Data Type of SMS, the CIoT GW 406 is not required to allocate anIP address, or send a Create Session Request to the P-GW 410.

At 4.5, during roaming scenarios, and depending on the Data Type, theP-GW 410 may send a Create Session response (or a new control message)to the CIoT GW 406. For the IP data case, the response can contain theallocated IP address.

At 4.6, the CIoT GW 406 can send a an Attach Accept (e.g., CIoT Attach)to the CIoT UE 402, such as through the CIoT eNB 404, for example,without any session management message. For a Data Type of IP, anallocated IP address can be sent to the CIoT UE 402.

At 4.7, the CIoT UE 402 can respond with an Attach Complete message,and, at 4.8, the RRC connection can be released.

FIG. 5 illustrates generally an example CIoT mobile originated (MO)small data transfer 500 including a CIoT UE 502, a CIoT eNB 504, a CIoTGW 506, and, in roaming scenarios, a Packet Data Network Gateway (P-GW)510.

At 5.0, an Attach Procedure can be performed, such as described above inFIG. 4. At 5.1, the CIoT UE 502 requests that an AS establish an RRCconnection. In an example, a new NAS message format can be used to carrythe small data packet (e.g., IP, non-IP, SMS) in an encryptedInformation Element (IE), such as a NAS PDU. The CIoT UE 502 can alsoindicate whether acknowledgment/response to the small data packet isexpected or not. There is no need to set up DRB and AS security.

In an example, the NAS PDU can include an unencrypted part includingeKSI or Sequence Number IEs as per usual for encrypted NAS messages. TheCIoT GW 506 can use the IE, and the S-TMSI, to identify the securitycontext to decrypt the small data packet.

At 5.2, the CIoT eNB 504 (e.g., a CIoT RAN) can forward the initial UEmessage to the CIoT GW 506. The initial UE message can include a NASPDU, encrypted data, and an acknowledgement/response indication. In thecase of multiple small data packet transmission, subsequent small datapackets may be contained in UL NAS transport without establishment of anRRC connection.

The CIoT GW 506 can check integrity protection and decrypt the NASmessage, obtaining the small data packet. At 5.4, the CIoT GW 506forwards the small data packet using appropriate mechanisms depending onData Type.

For example, the CIoT GW 506 may send IP small data over SGi. In roamingcase, the data may traverse through the P-GW 510. The CIoT GW 506 maysend SMS to SMS-SC/IWMSC. In certain examples, the procedure can be thesame as over an SGd interface defined for SMS in MME in Annex C of TS23.272. The CIoT GW 506 may send non-IP small data, depending on theconfiguration, to SCEF or to AS using point-to-point forwarding tunnel.

At 5.4, if no acknowledgment/response to the small data packet isexpected (based on the subscriber information and the Ack/Rsp indicationfrom the UE), the CIoT GW 506 can immediately release the connection.Otherwise, the CIoT GW 506 or the P-GW 510 (in case of roaming) canreceive a (response) small data packet.

At 5.5, the CIoT GW 506 can encrypt the NAS message with the downlinksmall data packet and send the downlink NAS message to the CIoT eNB 502(e.g., to a CIoT-RAN). The CIoT GW 506 may then release the signallingconnection after the timer monitoring the connection expires.

At 5.6, the CIoT eNB 504 can send the Downlink RRC message (e.g.,including the NAS message) to the CIoT UE 502, and release the RRCconnection after the timer monitoring the connection expires.

FIG. 6 illustrates generally an example CIoT mobile terminated (MT)small data transfer 600, including a CIoT UE 602, a CIoT eNB 604, a CIoTGW 606, and, in roaming scenarios, a Packet Data Network Gateway (P-GW)610.

At 6.0, an Attach Procedure can be performed, such as described above inFIG. 4. At 6.1, the CIoT GW 606 receives a small data packet (e.g., IP,non-IP, SMS). At 6.2, if there is no signalling connection with the CIoTUE 502, the CIoT GW 606 buffers the received small data packet, andpages the CIoT UE 502, which then sends the Service Request message toCIoT GW 606.

At 6.3, the CIoT GW 606 sends the small data packet in an encrypted IEin a NAS PDU in a Downlink NAS message and the CIoT eNB 604 sends theNAS PDU to the CIoT UE 502. In certain examples, DRB and AS security isnot required.

At 6.4, the CIoT UE 502 optionally sends a packet as an acknowledgementin an encrypted IE in a NAS PDU in an UL RRC message. The CIoT eNB 604can forward the NAS PDU to the CIoT GW 606. After the timer monitoringthe connection expires, the CIoT GW 606, the CIoT UE 502, and the CIoTeNB 604 release the connection locally.

At 6.5, the CIoT GW 606 optionally decrypts and forwards the NAS-PDU toan appropriate node, for example, depending on Data Type.

FIG. 7 illustrates generally a block diagram of an example UE 700 (e.g.,a CIoT UE) upon which one or more embodiments may be implemented. In anexample, the UE 700 may include application circuitry 702, basebandcircuitry 704, Radio Frequency (RF) circuitry 706, front-end module(FEM) circuitry 708 and one or more antennas 710, coupled together atleast as shown. As used with reference to FIG. 7, the term “circuitry”may refer to, be part of, or include an Application Specific IntegratedCircuit (ASIC), an electronic circuit, a processor (shared, dedicated,or group), and/or memory (shared, dedicated, or group) that execute oneor more software or firmware programs, a combinational logic circuit,and/or other suitable hardware components that provide the describedfunctionality.

The application circuitry 702 may include one or more applicationprocessors. For example, the application circuitry 702 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) may include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors may be coupledwith and/or may include memory/storage and may be configured to executeinstructions stored in the memory/storage to enable various applicationsand/or operating systems to run on the system.

The baseband circuitry 704 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 704 may include one or more baseband processorsand/or control logic to process baseband signals received from a receivesignal path of the RF circuitry 706 and to generate baseband signals fora transmit signal path of the RF circuitry 706. Baseband processingcircuitry 704 may interface with the application circuitry 702 forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 706. For example, the baseband circuitry704 may include a second generation (2G) baseband processor 704 a, thirdgeneration (3G) baseband processor 704 b, fourth generation (4G)baseband processor 704 c, and/or other baseband processor(s) 704 d forother existing generations, generations in development or to bedeveloped in the future (e.g., fifth generation (5G), 6G, etc.). Thebaseband circuitry 704 (e.g., one or more of baseband processors 704a-d) may handle various radio control functions that enablecommunication with one or more radio networks via the RF circuitry 706.The radio control functions may include, but are not limited to, signalmodulation/demodulation, encoding/decoding, radio frequency shifting,etc. In an example, modulation/demodulation circuitry of the basebandcircuitry 704 may include Fast-Fourier Transform (FFT), precoding,and/or constellation mapping/demapping functionality. In an example,encoding/decoding circuitry of the baseband circuitry 704 may includeconvolution, tail-biting convolution, turbo, Viterbi, and/or Low DensityParity Check (LDPC) encoder/decoder functionality. Embodiments ofmodulation/demodulation and encoder/decoder functionality are notlimited to these examples and may include other suitable functionalityin other embodiments.

In an example, the baseband circuitry 704 may include elements of aprotocol stack such as, for example, elements of an evolved universalterrestrial radio access network (EUTRAN) protocol including, forexample, physical (PHY), media access control (MAC), radio link control(RLC), packet data convergence protocol (PDCP), and/or radio resourcecontrol (RRC) elements. A central processing unit (CPU) 704 e of thebaseband circuitry 704 may be configured to run elements of the protocolstack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In anexample, the baseband circuitry may include one or more audio digitalsignal processor(s) (DSP) 704 f. The audio DSP(s) 704 f may be includeelements for compression/decompression and echo cancellation and mayinclude other suitable processing elements in other embodiments. In anexample, components of the baseband circuitry may be suitably combinedin a single chip, a single chipset, or disposed on a same circuit board.In an example, some or all of the constituent components of the basebandcircuitry 704 and the application circuitry 702 may be implementedtogether such as, for example, on a system on a chip (SOC).

In an example, the baseband circuitry 704 may provide for communicationcompatible with one or more radio technologies. For example, thebaseband circuitry 704 may support communication with an evolveduniversal terrestrial radio access network (EUTRAN) and/or otherwireless metropolitan area networks (WMAN), a wireless local areanetwork (WLAN), a wireless personal area network (WPAN). Embodiments inwhich the baseband circuitry 704 is configured to support radiocommunications of more than one wireless protocol may be referred to asmulti-mode baseband circuitry.

RF circuitry 706 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 706 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 706 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from the FEMcircuitry 708 and provide baseband signals to the baseband circuitry704. RF circuitry 706 may also include a transmit signal path which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 704 and provide RF output signals to the FEMcircuitry 708 for transmission.

In an example, the RF circuitry 706 may include a receive signal pathand a transmit signal path. The receive signal path of the RF circuitry706 may include mixer circuitry 706 a, amplifier circuitry 706 b andfilter circuitry 706 c. The transmit signal path of the RF circuitry 706may include filter circuitry 706 c and mixer circuitry 706 a. RFcircuitry 706 may also include synthesizer circuitry 706 d forsynthesizing a frequency for use by the mixer circuitry 706 a of thereceive signal path and the transmit signal path. In an example, themixer circuitry 706 a of the receive signal path may be configured todown-convert RF signals received from the FEM circuitry 708 based on thesynthesized frequency provided by synthesizer circuitry 706 d. Theamplifier circuitry 706 b may be configured to amplify thedown-converted signals and the filter circuitry 706 c may be a low-passfilter (LPF) or band-pass filter (BPF) configured to remove unwantedsignals from the down-converted signals to generate output basebandsignals. Output baseband signals may be provided to the basebandcircuitry 704 for further processing. In an example, the output basebandsignals may be zero-frequency baseband signals, although this is not arequirement. In an example, mixer circuitry 706 a of the receive signalpath may comprise passive mixers, although the scope of the embodimentsis not limited in this respect.

In an example, the mixer circuitry 706 a of the transmit signal path maybe configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 706 d togenerate RF output signals for the FEM circuitry 708. The basebandsignals may be provided by the baseband circuitry 704 and may befiltered by filter circuitry 706 c. The filter circuitry 706 c mayinclude a low-pass filter (LPF), although the scope of the embodimentsis not limited in this respect.

In an example, the mixer circuitry 706 a of the receive signal path andthe mixer circuitry 706 a of the transmit signal path may include two ormore mixers and may be arranged for quadrature downconversion and/orupconversion respectively. In an example, the mixer circuitry 706 a ofthe receive signal path and the mixer circuitry 706 a of the transmitsignal path may include two or more mixers and may be arranged for imagerejection (e.g., Hartley image rejection). In an example, the mixercircuitry 706 a of the receive signal path and the mixer circuitry 706 amay be arranged for direct downconversion and/or direct upconversion,respectively. In an example, the mixer circuitry 706 a of the receivesignal path and the mixer circuitry 706 a of the transmit signal pathmay be configured for super-heterodyne operation.

In an example, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 706 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry704 may include a digital baseband interface to communicate with the RFcircuitry 706.

In a dual-mode example, a separate radio IC circuitry may be providedfor processing signals for each spectrum, although the scope of theembodiments is not limited in this respect.

In an example, the synthesizer circuitry 706 d may be a fractional-Nsynthesizer or a fractional N/N+1 synthesizer, although the scope of theembodiments is not limited in this respect as other types of frequencysynthesizers may be suitable. For example, synthesizer circuitry 706 dmay be a delta-sigma synthesizer, a frequency multiplier, or asynthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 706 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 706 a of the RFcircuitry 706 based on a frequency input and a divider control input. Inan example, the synthesizer circuitry 706 d may be a fractional N/N+1synthesizer.

In an example, frequency input may be provided by a voltage controlledoscillator (VCO), although that is not a requirement. Divider controlinput may be provided by either the baseband circuitry 704 or theapplications processor 702 depending on the desired output frequency. Inan example, a divider control input (e.g., N) may be determined from alook-up table based on a channel indicated by the applications processor702.

Synthesizer circuitry 706 d of the RF circuitry 706 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In an example, the divider may be a dual modulus divider(DMD) and the phase accumulator may be a digital phase accumulator(DPA). In an example, the DMD may be configured to divide the inputsignal by either N or N+1 (e.g., based on a carry out) to provide afractional division ratio. In some example embodiments, the DLL mayinclude a set of cascaded, tunable, delay elements, a phase detector, acharge pump and a D-type flip-flop. In these embodiments, the delayelements may be configured to break a VCO period up into Nd equalpackets of phase, where Nd is the number of delay elements in the delayline. In this way, the DLL provides negative feedback to help ensurethat the total delay through the delay line is one VCO cycle.

In an example, synthesizer circuitry 706 d may be configured to generatea carrier frequency as the output frequency, while in other embodiments,the output frequency may be a multiple of the carrier frequency (e.g.,twice the carrier frequency, four times the carrier frequency) and usedin conjunction with quadrature generator and divider circuitry togenerate multiple signals at the carrier frequency with multipledifferent phases with respect to each other. In an example, the outputfrequency may be a LO frequency (fLO). In an example, the RF circuitry706 may include an IQ/polar converter.

FEM circuitry 708 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 710, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 706 for furtherprocessing. FEM circuitry 708 may also include a transmit signal pathwhich may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 706 for transmission by one ormore of the one or more antennas 710.

In an example, the FEM circuitry 708 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry may include a receive signal path and a transmit signal path.The receive signal path of the FEM circuitry may include a low-noiseamplifier (LNA) to amplify received RF signals and provide the amplifiedreceived RF signals as an output (e.g., to the RF circuitry 706). Thetransmit signal path of the FEM circuitry 708 may include a poweramplifier (PA) to amplify input RF signals (e.g., provided by RFcircuitry 706), and one or more filters to generate RF signals forsubsequent transmission (e.g., by one or more of the one or moreantennas 710.

In an example, the UE 700 may include additional elements such as, forexample, memory/storage, display, camera, sensor, and/or input/output(I/O) interface.

FIG. 8 illustrates generally a block diagram of an example machine 800upon which any one or more of the techniques (e.g., methodologies)discussed herein may perform. In alternative embodiments, the machine800 may operate as a standalone device or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine 800may operate in the capacity of a server machine, a client machine, orboth in server-client network environments. In an example, the machine800 may act as a peer machine in peer-to-peer (P2P) (or otherdistributed) network environment. The machine 800 may be a personalcomputer (PC), a tablet PC, a set-top box (STB), a personal digitalassistant (PDA), a mobile telephone, a web appliance, a network router,switch or bridge, or any machine capable of executing instructions(sequential or otherwise) that specify actions to be taken by thatmachine. Further, while only a single machine is illustrated, the term“machine” shall also be taken to include any collection of machines thatindividually or jointly execute a set (or multiple sets) of instructionsto perform any one or more of the methodologies discussed herein, suchas cloud computing, software as a service (SaaS), other computer clusterconfigurations.

Examples, as described herein, may include, or may operate by, logic ora number of components, or mechanisms. Circuit sets are a collection ofcircuits implemented in tangible entities that include hardware (e.g.,simple circuits, gates, logic, etc.). Circuit set membership may beflexible over time and underlying hardware variability. Circuit setsinclude members that may, alone or in combination, perform specifiedoperations when operating. In an example, hardware of the circuit setmay be immutably designed to carry out a specific operation (e.g.,hardwired). In an example, the hardware of the circuit set may includevariably connected physical components (e.g., execution units,transistors, simple circuits, etc.) including a computer readable mediumphysically modified (e.g., magnetically, electrically, moveableplacement of invariant massed particles, etc.) to encode instructions ofthe specific operation. In connecting the physical components, theunderlying electrical properties of a hardware constituent are changed,for example, from an insulator to a conductor or vice versa. Theinstructions enable embedded hardware (e.g., the execution units or aloading mechanism) to create members of the circuit set in hardware viathe variable connections to carry out portions of the specific operationwhen in operation. Accordingly, the computer readable medium iscommunicatively coupled to the other components of the circuit setmember when the device is operating. In an example, any of the physicalcomponents may be used in more than one member of more than one circuitset. For example, under operation, execution units may be used in afirst circuit of a first circuit set at one point in time and reused bya second circuit in the first circuit set, or by a third circuit in asecond circuit set at a different time.

Machine (e.g., computer system) 800 may include a hardware processor 802(e.g., a central processing unit (CPU), a graphics processing unit(GPU), a hardware processor core, or any combination thereof), a mainmemory 804 and a static memory 806, some or all of which may communicatewith each other via an interlink (e.g., bus) 808. The machine 800 mayfurther include a display unit 810 (e.g., a raster display, vectordisplay, holographic display, etc.), an alphanumeric input device 812(e.g., a keyboard), and a user interface (UI) navigation device 814(e.g., a mouse). In an example, the display unit 810, input device 812and UI navigation device 814 may be a touch screen display. The machine800 may additionally include a storage device (e.g., drive unit) 816, asignal generation device 818 (e.g., a speaker), a network interfacedevice 820, and one or more sensors 821, such as a global positioningsystem (GPS) sensor, compass, accelerometer, or other sensor. Themachine 800 may include an output controller 828, such as a serial(e.g., universal serial bus (USB), parallel, or other wired or wireless(e.g., infrared (IR), near field communication (NFC), etc.) connectionto communicate or control one or more peripheral devices (e.g., aprinter, card reader, etc.).

The storage device 816 may include a machine readable medium 822 onwhich is stored one or more sets of data structures or instructions 824(e.g., software) embodying or utilized by any one or more of thetechniques or functions described herein. The instructions 824 may alsoreside, completely or at least partially, within the main memory 804,within static memory 806, or within the hardware processor 802 duringexecution thereof by the machine 800. In an example, one or anycombination of the hardware processor 802, the main memory 804, thestatic memory 806, or the storage device 816 may constitute machinereadable media.

While the machine readable medium 822 is illustrated as a single medium,the term “machine readable medium” may include a single medium ormultiple media (e.g., a centralized or distributed database, and/orassociated caches and servers) configured to store the one or moreinstructions 824.

The term “machine readable medium” may include any medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine 800 and that cause the machine 800 to perform any one ormore of the techniques of the present disclosure, or that is capable ofstoring, encoding or carrying data structures used by or associated withsuch instructions. Non-limiting machine readable medium examples mayinclude solid-state memories, and optical and magnetic media. In anexample, a massed machine readable medium comprises a machine readablemedium with a plurality of particles having invariant (e.g., rest) mass.Accordingly, massed machine-readable media are not transitorypropagating signals. Specific examples of massed machine readable mediamay include: non-volatile memory, such as semiconductor memory devices(e.g., Electrically Programmable Read-Only Memory (EPROM), ElectricallyErasable Programmable Read-Only Memory (EEPROM)) and flash memorydevices; magnetic disks, such as internal hard disks and removabledisks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions 824 may further be transmitted or received over acommunications network 826 using a transmission medium via the networkinterface device 820 utilizing any one of a number of transfer protocols(e.g., frame relay, internet protocol (IP), transmission controlprotocol (TCP), user datagram protocol (UDP), hypertext transferprotocol (HTTP), etc.). Example communication networks may include alocal area network (LAN), a wide area network (WAN), a packet datanetwork (e.g., the Internet), mobile telephone networks (e.g., cellularnetworks), Plain Old Telephone (POTS) networks, and wireless datanetworks (e.g., Institute of Electrical and Electronics Engineers (IEEE)802.11 family of standards known as WiFi®, IEEE 802.16 family ofstandards known as WiMax®), IEEE 802.15.4 family of standards,peer-to-peer (P2P) networks, among others. In an example, the networkinterface device 820 may include one or more physical jacks (e.g.,Ethernet, coaxial, or phone jacks) or one or more antennas to connect tothe communications network 826. In an example, the network interfacedevice 820 may include a plurality of antennas to wirelessly communicateusing at least one of single-input multiple-output (SIMO),multiple-input multiple-output (MIMO), or multiple-input single-output(MISO) techniques. The term “transmission medium” shall be taken toinclude any intangible medium that is capable of storing, encoding orcarrying instructions for execution by the machine 800, and includesdigital or analog communications signals or other intangible medium tofacilitate communication of such software.

Embodiments of the technology herein may be described as related to theThird Generation Partnership Project (3GPP) long term evolution (LTE) orLTE-advanced (LTE-A) standards. For example, terms or entities such aseNodeB (eNB), mobility management entity (MME), user equipment (UE),etc., may be used that may be viewed as LTE-related terms or entities.However, in other embodiments the technology may be used in or relatedto other wireless technologies such as the IEEE 802.16 wirelesstechnology (WiMax), IEEE 802.11 wireless technology (WiFi), variousother wireless technologies such as global system for mobilecommunications (GSM), enhanced data rates for GSM evolution (EDGE), GSMEDGE radio access network (GERAN), universal mobile telecommunicationssystem (UMTS), UMTS terrestrial radio access network (UTRAN), or other2G, 3G, 4G, 5G, etc. technologies either already developed or to bedeveloped. In those embodiments, where LTE-related terms such as eNB,MME, UE, etc. are used, one or more entities or components may be usedthat may be considered to be equivalent or approximately equivalent toone or more of the LTE-based terms or entities.

Additional Notes and Examples

Example 1 may include a User Equipment (UE) configured to operate as aspecial Cellular IoT Device.

Example 2 may include the UE in example 1 or some other example herein,wherein the UE is to interface with a CIoT Access Network (CAN) over aC1 reference point.

Example 3 may include the UE in example 1 or some other example herein,wherein the UE is to support a lightweight NAS protocol where UL/DL datatransport is supported over new radio type interfacing with CIoT AccessNetwork (CAN) over C1 reference point.

Example 4 may include the UE in example 1 or some other example herein,wherein the UE is to support a L2 tunnel for data transfer to CAN.

Example 5 may include a network comprising one or more Cellular IoTAccess Gateways (CANs).

Example 6 may include the network in example 1 or 5 or some otherexample herein, where CIoT GW Supporting lightweight NAS protocol whereUL/DL data transport is supported over new radio type interfacing withCIoT UE over C1 reference point.

Example 7 may include the network in example 1 or 5 or some otherexample herein, Supporting L2 tunnel for data transfer to/from UE.

Example 8 may include the network in example 1 or 5 or some otherexample herein, Supporting S1-Lite interface towards eNB.

Example 9 may include the network in example 1 or 5 or some otherexample herein, Supporting sub-set of functionality of MME, S-GW, P-GW.

Example 10 may include the network in example 1 or 5 or some otherexample herein, Supporting C2 reference point towards MME for exchangeof authentication parameters.

Example 11 may include the network in example 1 or 5 or some otherexample herein, Supporting C2 reference point towards HSS/AAA forexchange of authentication parameters.

Example 12 may include the network in example 1 or 5 or some otherexample herein, Supporting C4 reference point towards SCEF for exchangeof information with Application Servers.

Example 13 may include the network in example 1 or 5 or some otherexample herein, Supporting C3 reference point towards AS for exchange ofIP data.

Example 14 may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of examples1-13, or any other method or process described herein.

Example 15 may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of examples 1-13, or any other method or processdescribed herein.

Example 16 may include an apparatus comprising control logic, transmitlogic, and/or receive logic to perform one or more elements of a methoddescribed in or related to any of examples 1-13, or any other method orprocess described herein.

Example 17 may include a method of communicating in a wireless networkas shown and described herein.

Example 18 may include a system for providing wireless communication asshown and described herein.

Example 19 may include a device for providing wireless communication asshown and described herein.

Example 20 is an apparatus of a Cellular Internet-of-Things (CIoT) UserEquipment (UE), the apparatus comprising: processing circuitry toprocess data for communication with a network through a CIoT enhancedNode B (eNB) according to a lightweight Non-Access Stratum (NAS)protocol; and a radio interface to communicate with the CIoT eNB using afirst reference point.

In Example 21, the subject matter of Example 20 optionally includes,wherein the lightweight NAS protocol supports a reduced set of NASmessages for CIoT devices exclusive of mobile NAS messages.

In Example 22, the subject matter of Example 21 optionally includes,wherein the mobile NAS messages include at least one of attach ortracking area update (TAU).

In Example 23, the subject matter of any one or more of Examples 20-22optionally include, wherein the processing circuitry is configured toreceive a modified NAS message that includes communication data from thenetwork.

In Example 24, the subject matter of any one or more of Examples 20-23optionally include, wherein the processing circuitry is configured tomodify an existing NAS message to include data for communication to thenetwork.

In Example 25, the subject matter of any one or more of Examples 20-24optionally include, wherein the CIoT eNB is configured to communicatewith the CIoT UE and to terminate the first reference point, wherein thefirst reference point is a narrow-band air interface between the CIoT UEand the CIoT eNB, and wherein the network is an operator network or acloud service network.

Example 26 is an apparatus of a Cellular Internet-of-Things (CIoT)enhanced Node B (eNB), the apparatus comprising: processing circuitry toprocess data for communication between a CIoT User Equipment (UE) and anetwork according to a lightweight Non-Access Stratum (NAS) protocol;and a radio interface to communicate with the CIoT UE using a firstreference point.

In Example 27, the subject matter of Example 26 optionally includes,wherein the lightweight NAS protocol supports a reduced set of NASmessages for CIoT devices exclusive of mobile NAS messages.

In Example 28, the subject matter of Example 27 optionally includes,wherein the mobile NAS messages include at least one of attach ortracking area update (TAU).

In Example 29, the subject matter of any one or more of Examples 26-28optionally include, wherein the processing circuitry is configured tomodify an existing NAS message to include data for communication to theCIoT UE.

In Example 30, the subject matter of Example 29 optionally includes,wherein the existing NAS message includes an attach message or a servicerequest message.

In Example 31, the subject matter of any one or more of Examples 29-30optionally include, wherein the existing NAS message includes a periodictracking area update (TAU) message.

In Example 32, the subject matter of any one or more of Examples 26-31optionally include, wherein the processing circuitry is configured toreceive data for communication to the network in a modified NAS messagefrom the CIoT UE.

In Example 33, the subject matter of any one or more of Examples 26-32optionally include, wherein the CIoT eNB is a component of a CIoT AccessNetwork (CAN) including a CIoT Gateway (GW) coupled to a plurality ofCIoT eNBs, wherein the CIoT GW is configured to communicate with thenetwork using a second reference point, wherein the first referencepoint is a narrow-band air interface between the CIoT UE and the CIoTeNB, and the second reference point includes an air interface betweenthe CIoT GW and the network, and wherein the network is an operatornetwork or a cloud service network.

In Example 34, the subject matter of Example 33 optionally includes,wherein the CIoT GW includes functionality of at least one of a MobileManagement Entity (MME), Serving Gateway (S-GW), and Packet Data NetworkGateway (P-GW).

Example 35 is at least one machine readable medium of a CellularInternet-of-Things (CIoT) User Equipment (UE), the machine readablemedium including instructions that, when executed by the CIoT UE,configure the CIoT UE to: process data for communication with a networkthrough a CIoT enhanced Node B (eNB) according to a lightweightNon-Access Stratum (NAS) protocol using processing circuitry; andcommunicate with the CIoT eNB using a radio interface and a firstreference point.

In Example 36, the subject matter of Example 35 optionally includes,wherein the lightweight NAS protocol supports a reduced set of NASmessages for CIoT devices exclusive of mobile NAS messages, wherein thefirst reference point is a narrow-band air interface between the CIoT UEand the CIoT eNB, and wherein the mobile NAS messages including at leastone of attach or tracking area update (TAU).

In Example 37, the subject matter of any one or more of Examples 35-36optionally include, the machine readable medium including instructionsthat, when executed by the CIoT UE, configure the CIoT UE to: receive amodified NAS message that includes communication data from the network;or modify an existing NAS message to include data for communication tothe network.

Example 38 is at least one machine readable medium of a CellularInternet-of-Things (CIoT) enhanced Node B (eNB), the machine readablemedium including instructions that, when executed by the CIoT eNB,configure the CIoT eNB to: process data for communication between a CIoTUser Equipment (UE) and a network according to a lightweight Non-AccessStratum (NAS) protocol using processing circuitry; and communicate withthe CIoT UE using a radio interface and a first reference point.

In Example 39, the subject matter of Example 38 optionally includes,wherein the lightweight NAS protocol supports a reduced set of NASmessages for CIoT devices exclusive of mobile NAS messages.

In Example 40, the subject matter of Example 39 optionally includes,wherein the first reference point is a narrow-band air interface betweenthe CIoT UE and the CIoT eNB, and wherein the mobile NAS messagesincluding at least one of attach or tracking area update (TAU).

In Example 41, the subject matter of any one or more of Examples 38-40optionally include, the machine readable medium including instructionsthat, when executed by the CIoT eNB, configure the CIoT eNB to: modifyan existing NAS message to include data for communication to the CIoTUE.

In Example 42, the subject matter of any one or more of Examples 38-41optionally include, wherein the existing NAS message includes an attachmessage, a service request message, or a periodic tracking area update(TAU) message.

In Example 43, the subject matter of any one or more of Examples 38-42optionally include, the machine readable medium including instructionsthat, when executed by the CIoT eNB, configure the CIoT eNB to: receivedata for communication to the network in a modified NAS message from theCIoT UE.

In an example, a system or apparatus can include, or can optionally becombined with any portion or combination of any portions of any one ormore of the examples illustrated above to include, means for performingany one or more of the functions of the examples illustrated above, or anon-transitory machine-readable medium including instructions that, whenperformed by a machine, cause the machine to perform any one or more ofthe functions of the examples illustrated above.

The above detailed description includes references to the accompanyingdrawings, which form a part of the detailed description. The drawingsshow, by way of illustration, specific embodiments in which theinvention can be practiced. These embodiments are also referred toherein as “examples.” Such examples can include elements in addition tothose shown or described. However, the present inventors alsocontemplate examples in which only those elements shown or described areprovided. Moreover, the present inventors also contemplate examplesusing any combination or permutation of those elements shown ordescribed (or one or more aspects thereof), either with respect to aparticular example (or one or more aspects thereof), or with respect toother examples (or one or more aspects thereof) shown or describedherein.

All publications, patents, and patent documents referred to in thisdocument are incorporated by reference herein in their entirety, asthough individually incorporated by reference. In the event ofinconsistent usages between this document and those documents soincorporated by reference, the usage in the incorporated reference(s)should be considered supplementary to that of this document; forirreconcilable inconsistencies, the usage in this document controls.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In the appended claims, the terms “including” and“in which” are used as the plain-English equivalents of the respectiveterms “comprising” and “wherein.” Also, in the following claims, theterms “including” and “comprising” are open-ended, that is, a system,device, article, or process that includes elements in addition to thoselisted after such a term in a claim are still deemed to fall within thescope of that claim. Moreover, in the following claims, the terms“first,” “second,” and “third,” etc. are used merely as labels, and arenot intended to impose numerical requirements on their objects.

Method examples described herein can be machine or computer-implementedat least in part. Some examples can include a computer-readable mediumor machine-readable medium encoded with instructions operable toconfigure an electronic device to perform methods as described in theabove examples. An implementation of such methods can include code, suchas microcode, assembly language code, a higher-level language code, orthe like. Such code can include computer readable instructions forperforming various methods. The code may form portions of computerprogram products. Further, the code can be tangibly stored on one ormore volatile or non-volatile tangible computer-readable media, such asduring execution or at other times. Examples of these tangiblecomputer-readable media can include, but are not limited to, hard disks,removable magnetic disks, removable optical disks (e.g., compact disksand digital video disks), magnetic cassettes, memory cards or sticks,random access memories (RAMs), read only memories (ROMs), and the like.

The above description is intended to be illustrative, and notrestrictive. For example, the above-described examples (or one or moreaspects thereof) may be used in combination with each other. Otherembodiments can be used, such as by one of ordinary skill in the artupon reviewing the above description. The Abstract is provided to allowthe reader to quickly ascertain the nature of the technical disclosure.It is submitted with the understanding that it will not be used tointerpret or limit the scope or meaning of the claims. Also, in theabove Detailed Description, various features may be grouped together tostreamline the disclosure. This should not be interpreted as intendingthat an unclaimed disclosed feature is essential to any claim. Rather,inventive subject matter may lie in less than all features of aparticular disclosed embodiment. Thus, the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate embodiment, and it is contemplated that suchembodiments can be combined with each other in various combinations orpermutations. The scope of the invention should be determined withreference to the appended claims, along with the full scope ofequivalents to which such claims are entitled.

What is claimed is:
 1. An apparatus of a mobility management entity(MME), the apparatus comprising: memory; and processing circuitrycoupled to the memory wherein to transfer data in Non-Access-Stratum(NAS) protocol data units (PDUs), the processing circuitry is configuredto: decode an attach request, sent from a user equipment (UE), theattach request indicating the UE supports a cellular internet-of-things(CIoT) optimization; encode, for transmission to the UE, an attachaccept message based on the attach request; decode an attach completemessage, sent from the UE, based on the attach accept message; decode aninitial UE message, the initial UE message sent from the UE over an aradio resource control (RRC) connection, the initial UE messageincluding a NAS PDU, and the NAS PDU including encrypted uplink data,the NAS PDU received from the UE without establishment of a bearer inaccordance with the CIoT optimization, the NAS PDU comprising anidentity of a bearer for a packet data network (PDN) connectionassociated with the uplink data; check integrity of the NAS PDU; decryptthe encrypted uplink data from the NAS PDU, wherein the memory isconfigured to store the decrypted uplink data; and encode the decrypteduplink data for transmission to a PDN gateway (P-GW).
 2. The apparatusof claim 1, wherein the NAS PDU includes an acknowledgment or responseindication.
 3. The apparatus of claim 2, wherein the processingcircuitry is configured to release a signalling connection for the UEbased on the acknowledgement or response indication, and wherein if theNAS PDU does not include release information, the acknowledgementincludes an indication of a bearer established for further uplink datatransmission.
 4. The apparatus of claim 2, wherein the processingcircuitry is configured to: decode downlink data in response to thedecrypted uplink data; encrypt the downlink data; and encode a downlinkNAS PDU that includes the encrypted downlink data for the UE.
 5. Theapparatus of claim 4, wherein the processing circuitry is configured to:determine no NAS PDU activity for a time period; and release asignalling connection for the UE based on the no NAS PDU activity forthe time period.
 6. The apparatus of claim 1, wherein the processingcircuitry is configured to update a location of the UE based on a changein a location of the UE.
 7. The apparatus of claim 1, wherein the attachrequest indicates a packet data network (PDN) connectivity request and aPDN type information element (IE) for a type of address.
 8. Theapparatus of claim 7, wherein the PDN type IE indicates an IPv4 addressor IPv6 address.
 9. The apparatus of claim 7, wherein the processingcircuitry is configured to establish a default bearer based on the PDNconnectivity request.
 10. A computer-readable storage medium that storesinstructions for execution by processing circuitry of a mobilitymanagement entity (MME) to configure to transfer data inNon-Access-Stratum (NAS) protocol data units (PDUs), the processingcircuitry configured to: decode an attach request, sent from a userequipment (UE), the attach request indicating the UE supports a cellularinternet-of-things (CIoT) optimization; encode, for transmission to theUE, an attach accept message based on the attach request; decode anattach complete message, sent from the UE, based on the attach acceptmessage; decode an initial UE message, the initial UE message sent fromthe UE over an a radio resource control (RRC) connection, the initial UEmessage including a NAS PDU, and the NAS PDU including encrypted uplinkdata, the NAS PDU received from the UE without establishment of a bearerin accordance with the CIoT optimization, the NAS PDU comprising anidentity of a bearer for a packet data network (PDN) connectionassociated with the uplink data; check integrity of the NAS PDU; decryptthe encrypted uplink data from the NAS PDU; and encode the decrypteduplink data for transmission to a PDN gateway (P-GW).
 11. Thecomputer-readable storage medium of claim 10, wherein the NAS PDUincludes an acknowledgment or response indication.
 12. Thecomputer-readable storage medium of claim 11, wherein the processingcircuitry is configured to release a signalling connection for the UEbased on the acknowledgement or response indication, and wherein if theNAS PDU does not include release information, the acknowledgementincludes an indication of a bearer established for further uplink datatransmission.
 13. The computer-readable storage medium of claim 11,wherein the processing circuitry is configured to: decode downlink datain response to the decrypted uplink data; encrypt the downlink data; andencode a downlink NAS PDU that includes the encrypted downlink data forthe UE.
 14. The computer-readable storage medium of claim 13, whereinthe processing circuitry is configured to: determine no NAS PDU activityfor a time period; and release a signalling connection for the UE on theno NAS PDU activity for the time period.
 15. The computer-readablestorage medium of claim 10, wherein the processing circuitry isconfigured to update a location of the UE based on a change in alocation of the UE.
 16. The computer-readable storage medium of claim10, wherein the attach request indicates a packet data network (PDN)connectivity request and a PDN type information element (IE) for a typeof address.
 17. The computer-readable storage medium of claim 16,wherein the PDN type IE indicates an IPv4 address or IPv6 address. 18.The computer-readable storage medium of claim 16, wherein the processingcircuitry is configured to establish a default bearer based on the PDNconnectivity request.